-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch main branch in grizzly #11
base: main
Are you sure you want to change the base?
Conversation
/otterdog validate |
This is your friendly self-service bot. Diff for 9932307Project ee4j[github_id=eclipse-ee4j]
!
! Warning: repository[name="jersey.github.io"] has 'gh_pages_build_type' with value 'workflow', but no
! corresponding 'github-pages' environment, please add such an environment.
!
there have been 85 validation infos, enable verbose output to display them.
! repository[name="grizzly"] {
! default_branch = "master" -> "main"
! }
- remove branch_protection_rule[pattern="master", repository=grizzly] {
- allows_deletions = false
- allows_force_pushes = false
- blocks_creations = false
- bypass_force_push_allowances = []
- bypass_pull_request_allowances = []
- dismisses_stale_reviews = false
- is_admin_enforced = false
- lock_allows_fetch_and_merge = false
- lock_branch = false
- pattern = "master"
- require_last_push_approval = false
- required_approving_review_count = 1
- requires_code_owner_reviews = false
- requires_commit_signatures = false
- requires_conversation_resolution = false
- requires_deployments = false
- requires_linear_history = false
- requires_pull_request = true
- requires_status_checks = false
- restricts_pushes = false
- restricts_review_dismissals = false
- }
+ add branch_protection_rule[pattern="main", repository=grizzly] {
+ allows_deletions = false
+ allows_force_pushes = false
+ blocks_creations = false
+ bypass_force_push_allowances = []
+ bypass_pull_request_allowances = []
+ dismisses_stale_reviews = false
+ is_admin_enforced = false
+ lock_allows_fetch_and_merge = false
+ lock_branch = false
+ pattern = "main"
+ require_last_push_approval = false
+ required_approving_review_count = 1
+ requires_code_owner_reviews = false
+ requires_commit_signatures = false
+ requires_conversation_resolution = false
+ requires_deployments = false
+ requires_linear_history = false
+ requires_pull_request = true
+ requires_status_checks = false
+ restricts_pushes = false
+ restricts_review_dismissals = false
+ }
Plan: 1 to add, 1 to change, 1 to delete. |
/otterdog check-sync |
This is your friendly self-service bot. The current configuration is in-sync with the live settings. 🚀 |
/otterdog team-info |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This looks fine to me, seeing the last commit to |
One note, is that I don't know who has access to change that, is that something the committer team needs to bring up some place to get updated? |
@arjantijms any comments? |
I just think we should be consistent here if we update the default branch to |
This PR is for that - to change it. Not to rename.
We have the access to change that, here with this PR. It's the matter of merging this, and EF magic will propagate change to repository. I'd like to see comments from grizzly team to reject or accept it. I'm not part of grizzly team myself, and have no idea if using
This PR is about changing default branch to the existing
For similar to happen there - committer can create new branch of current master (not me). And then change default branch to new one - with PR here. It's unclear for me why some PRs went to new |
@pzygielo, thank you for the explanation this all makes sense to me now. I'm not sure who created the |
Target of some latest PRs, like
suggests that
main
is the new default branch in repository.@anajosep, please check and approve or reject this PR.
Or perhaps @arjantijms or @pnicolucci could do that as well.